Hm. This is obviously a bug and obviously needs fixing, but I'm not sure I like this way of fixing it. limit.value is indeed used for the output filename, but it's also actually passed into a widget; I don't think it's a good idea to lie to a widget about which repository it's being run for (even though widgets aren't meant to differentiate their behaviour based on that). Since we know that we want everything smashed to lowercase, I think it might be better to either set limit.title (which is already used to override output filenames, and isn't looked at by widgets) or to explicitly smash case on outputFile in assembleDashboard, rather than setting the repo name to be potentially (case-)different from the actual repo name before passing it into a widget at all.

I updated the PR to lowercase slugs instead of modifying limit.value.

@stuartlangridge Happy with the updated PR?